I'm not able to print to my HP Laserjet 4000 printer when I use Ubuntu 8.04 (Hardy). When I use Ubuntu 7.10 (Gutsy) on the same PC (another partition 1f40 with dual boot) it all works fine. I installed the printer on the same way. Re-installing the printer doesn't help. Removing hplip and CUPS and re-installing these packages does't help.
Even re-installing Hardy doesn't help

When I try to print anything the printopdrachtbeheerder (screen where I see the printing commands) sometimes accepts the printcommand, and sometimes it doesn't. After a while it asks me If the printer is connected or not.

When in a console I give this command: sudo hp-check -r
it gives one error and one warning:

There are no CUPS printer queues found

and

Checking SIP version...
error: SIP not installed or version not found.

Checking for CUPS...
Status: taakplanner is actief
Version: 1.3.7
error_log is set to level: warn

I cant find a way to add any CUPS printer Queue and SIP is not in my repositories.


I can ping the printserver. It has a valid IP nr (192.168.2.10) and replies. I can login to the printserver and find all the communication methods are turned on.

I tried: socket://192.168.2.10:9100 as printer port. Does't work (though it works in Gutsy (7.10)
I tried ipp://192.168.2.10/printers/1 Doesn't work
I tried lpd://192.168.2.10 Doesn't work

The printer cannot be browsed for (it couldn't in 7.10 Gutsy too)

I tried tot install hplip 2.8.4 from the HP website without any result. The HP device manager that comes with it doesn't see the connected printer.

What can I do apart from downgrading to Ubuntu 7.10 ?

Any help or suggestions would be very nice.

Jeroen

Could it be this problem?

In hardy my HP printer was not detected anymore also, and after I added ",[my username]" in the "scanner:105:hplip" line in the /etc/group file it solved the problem.

(scanner:105:hplip -> scanner:105:hplip,username)

( = two dots (":") and an "x", not an angry face as it is automatically converted)

/var/log/cups/error.log shows this:

E [07/May/2008:22:57:21 +0200] [Job 30] kan worden hersteld: niet mogelijk om verbinding te maken met printer; nieuwe poging over 30 seconden...
E [07/May/2008:22:57:29 +0200] PID 7415 (/usr/lib/cups/backend/lpd) stopped with status 1!
E [07/May/2008:23:05:44 +0200] [Job 32] kan worden hersteld: niet mogelijk om verbinding te maken met printer; nieuwe poging over 30 seconden...
E [07/May/2008:23:09:23 +0200] [Job 32] kan worden hersteld: niet mogelijk om verbinding te maken met printer; nieuwe poging over 30 seconden...
E [07/May/2008:23:13:02 +0200] [Job 32] kan worden hersteld: niet mogelijk om verbinding te maken met printer; nieuwe poging over 30 seconden...
E [07/May/2008:23:16:41 +0200] [Job 32] kan worden hersteld: niet mogelijk om verbinding te maken met printer; nieuwe poging over 30 seconden...
E [07/May/2008:23:17:17 +0200] PID 7520 (/usr/lib/cups/backend/lpd) stopped with status 1!
E [07/May/2008:23:22:27 +0200] PID 7528 (/usr/lib/cups/backend/lpd) stopped with status 1!
E [07/May/2008:23:27:38 +0200] PID 7533 (/usr/lib/cups/backend/lpd) stopped with status 1!
E [07/May/2008:23:29:20 +0200] Release-Job: Unauthorized
E [07/May/2008:23:29:26 +0200] PID 7563 (/usr/lib/cups/backend/lpd) stopped with status 1!
E [07/May/2008:23:29:26 +0200] [Job 32] Canceling job since it could not be sent after 5 tries.
E [07/May/2008:23:32:49 +0200] Purge-Jobs: Unauthorized
E [07/May/2008:23:32:49 +0200] Purge-Jobs: Unauthorized
E [07/May/2008:23:35:01 +0200] PID 7688 (/usr/lib/cups/backend/lpd) stopped with status 1!
E [09/May/2008:00:07:43 +0200] [Job 35] kan worden hersteld: niet mogelijk om verbinding te maken met printer; nieuwe poging over 30 seconden...

No need. Putting the cupsd Apparmor profile in to 'complain' mode is sufficient - and we've already proven that Apparmor isn't to blame. You can put Apparmor back in to 'enforce' mode now:
Is there anything in /var/log/cups/error_log?

Did printing work after you put Apparmor in to complain mode?

The errors you listed suggest something wrong with the entries in /var/log/messages, which is causing logprof to choke. If printing works with Apparmor disabled, then I'll tell you how to clean your message log and get the relevant data.

Apparmor is in complain mode, but I still cant print. I get messages that the printer probably isn't connected.

How could I disable apparmor?

What could I do now?

Try:
This will put Apparmor in to 'complain' mode for the cupsd process. If it works in complain mode, then Apparmor is blocking file access somewhere.

If this is the case, try:
...to see what accesses are being blocked

I get this answer:

jeroen@adonet:~$ sudo aa-complain cupsd
[sudo] password for jeroen:
Setting /etc/apparmor.d/usr.sbin.cupsd to complain mode.
jeroen@adonet:~$ sudo logprof
Reading log entries from /var/log/messages.
Updating AppArmor profiles in /etc/apparmor.d.
Use of uninitialized value in string eq at /usr/share/perl5/Immunix/SubDomain.pm line 3377.
Use of uninitialized value in string eq at /usr/share/perl5/Immunix/SubDomain.pm line 3377.

Repository: http://apparmor.test.opensuse.org/backend/api

Would you like to enable access to the
profile repository?

(E)nable Repository / (D)isable Repository / Ask Me (L)ater

translation:
[Job35] can be repaired: not possible to make a connection with printer; new attempt in 30 seconds....

I'm having both. A new install on a desktop machine and a update from Gutsy on my notebook. Both are having the same problem

Hans - desperately waiting for a solution

Hans,

is it possible to boot your from gutsy updated installation of Hardy with an older Kernel. (normally you can choose the kernel in the GRUB menu from which ubuntu normally starts.) Preferably the old gutsy kernel?
And if so ,do you then still haven't any printing possibility?

I'm trying to find out if it is a problem in the new linux kernel that is used in Hardy. perhaps that offers a key to a solution.

Jeroen

Yeeessss - it's working with the old kernel 2.6.22-14-rt and -generic

Thank you very much for your suggestion!! This really keeps me going till the new kernel is fixed.

Hans

Hans,

I'll try it out this wee 1f40 k (first with a copy of ubuntu 7.10) before ruining my working copy)

Anyone any Idea where to post this bug in the hardy kernel?
Jeroen

Hi Jeroen,

There is a new kernel-version (2.6.24-17) in the recent update. Everything is working fine now

Thank you very much for your help.

Hans

I just updated my desktop machine as well and I'm still facing the same problem - Why?? The only difference between the two systems is that the desktop machine has a fresh install with Kubuntu (KDE-Desktop) and my working notebook installation is a update from gutsy with gnome desktop.
The notebook is working with the -rt kernel and the desktop machine is running the -generic kernel. Might this be a issue?

Hans

I would strongly recommend the HP Toolbox app!

System-Administraion-Printing
Add new printer
Choose HP laserjet 4000 is listaed

I have the updated kernel as well, but still can't print using hardy ande the printserver. I even installed the older gutsy kernel, but that makes the system run in low graphics mode. That's even worse.
I can only print from Windows or from ubuntu gutsy (7.10) Ubuntu 8.04 with both kernels don't print.

any other Ideas?

since the new update from yesterday I lost my ability to print again
This is really annoying!
hplip and stuff is installed. I'm working with all sorts of Linux for years and never ever had such problems to get a printer running.

Hans

Thanks, but no, my username was already in that group. My printer is NOT a USb printer. Its a parallel HP Laserjet 4000 printer connected to a sitecom printserver. The printserver is connected to my router with a fixed IP address. If I ping this IP nr, I receive nice answers. So the printserver is connected
In Gutsy I use printerpoort

and it works. In Hardy it doesn't.

doesn't see my printer and I can't print.

Does anyone have another idea?

Thanks

As far as I know the lpd command is lpd://192.168.2.10/L1 how about trying that?
Also try the ipp command using: ipp//192.168.2.10/ipp/P1
or ipp//192.168.2.10:631/ipp/P1

I have an epson that used to work under gutsy but doesn't under hardy, printing via a 3com print server. Unfortunately the printserver itself died a day ago, so perhaps that was the main problem for me!

However when it was working I setup a new printer under the GNOME printing screen from the main menus and chose "LPD" as the type of printer. The key entry was the "L1" which isn't intuitive but has to be used and must go in the queue field for the thing to work. It did the trick for me, hope it works for you, otherwise I can't help you more.

I also lost printing ability after Hardy installed. I send a job to cups, then cups stops it. I checked dmesg and this is what I get:

[16394.427672] audit(1211154077.674:6): type=1503 operation="inode_permission" requested_mask="::rw" denied_mask="::rw" name="/dev/tty" pid=23459 profile="/usr/sbin/cupsd" namespace="default"

It is a usb printer and appears to be connected:

[15619.787827] usblp0: USB Bidirectional printer dev 4 if 0 alt 0 proto 2 vid 0x04B8 pid 0x0005
[15619.787851] usbcore: registered new interface driver usblp

I thought it may be a permission issue, so I tried to print as root. Same thing.

I looked in /var/log/cups/error_log and got this:

E [18/May/2008:16:27:12 -0700] [Job 114] ijsgutenprint: the version of Gutenprint software installed (5.0.2) does not match the PPD file (5.0.1).
E [18/May/2008:16:27:12 -0700] [Job 114] ijsgutenprint: bad key code -4

So I tried reinstalling the printer. Nope.

Any ideas?

Adding yourself to the USB users might help if you've got an USB connected printer. There are threads about that issue.

This thread is about printing via the router to a printserver connected printer.

The lpd command responds that it is connected to the printer. A print command from yesterday rolls out of the printer, but nothing happens but waiting for half an hour.

Three days later still waiting....

Doesn't anybody have this problem. Doesn't somebody have a solution? I0d like to be able to print. from hardy.

Adonet,

I just found your thread and like you, am having trouble printing via LPD in Hardy. I've installed Hardy on my Acer 3003LCi laptop. My printer is a Samsung ML1710 served by a Trendnet ethernet to USB print server.

With Dapper through Gutsy, it has been pretty easy to get printing configured on this machine. But with Hardy, I still haven't had any luck. When I try to print a document, the Samsung starts to run, but then enters an error state. So I have to power off the printer to reset it. All other printers on the network print without issue.

So you are not alone, but I have not yet solved the problem. If I find something, I will let you know.

Red

Putting it in complain mode worked for me... what now?

Hello again,

I was finally able to try putting AppArmor into complain mode and that allowed my Hardy install to print to my Samsung printer. So what do I need to do from here to re-enable AppArmor but still continue getting printing to work? Is there a thread that describes the process to reconfigure around offending issues? This seems to be my last problem with Hardy that I need to get resolved.

Thanks for everyone help so far.

Red

I'm glad you can print at last. Look for an AppArmor specialist who might help you.

AppArmor in complainmode didn't do anything for me. So that isn't the problem for me.
Is there anybody who didn't make a fresh install of Hardy, but an upgrade from gutsy who has the same problem?

Is booting Hardy with the older Gutsy kernel probably a solution?

Hans,

I think we should make a bug report of this printing issue. I couldn't make a working updated version of ubuntu 710 to 804. Something went wronso I made a fresh installation of 804 (again) and installed the older 7.10 kernel 2.6.22-14. I can boot with that kernel, but only in low graphics mode. and that's not an option for me.

I'm still using ubuntu 7.10 and porinting is working fine, but I don't like the fact that I can't update openoffice to version 2.4 , stellarium to version 9.10 and so on and so on.

I know I can print from suse, from PC LinuxOS and from Ubuntu 6.10, 7.04 and 7.10.

A guy from HP couldn't help me in another forum and no-one seems to know the answer.

really disappointing

Jeroen

Doesn't work either. We think its a kernel issue.

I have the same problem. Unable to print. Printer connected to a parallel port print server through the LAN. See my post:

http://ubuntuforums.org/showthread.php?t=797508


The upgrade to kernel 2.6.24-17-generic did not change anything.

I reported a bug in:
https://bugs.launchpad.net/ubuntu/+bug/235197
please add your bug to this report, so ubuntu starts a repair procedure.

Jeroen

My SAMSUNG ML-2015 don't print anything since upgrade from 7.10 to 8.04 too. I've tryed these things like cups protections and apparmor. don't works now. After searching internet i decided to put it here.
but, am. i still don't know how to change kerner i'm using. any help with this?

edit:
ok, downloading a new driver helped. But one interesting thing - there is no driver for ML 2015 in samsung.com, so i used one for ML 2010.

You've probably got a driver problem. Please start another thread for that. I don't have a driver problem since the printer is working OK from 7.10 but isn't from 8.04 with the same configuration and driver.

Hey everyone,

Since there was a new kernel update today that brought it to: 2.6.24-18-generic, I thought I would try printing over the network again. It still does not work, and the symptoms are the same. Anyone else have a different experience?

I tested the print function with the new kernel, but still nothing comes out of the printer. I continue to use ubuntu 7.10. to be able to print.

I don't get any reaction on the ubuntu bug reporting site. It seems as if no-one is reading them.

Perhaps it's wise to make an orientation to another distro?

Agreed adonet.

I've got my eye on Debian Linux and Arch Linux.
If things don't get fixed around here soon enough I'm gonna have to jump ship.

I find it very sad to see a previously solid distribution like Ubuntu sink to the lows of what we have seen in version 8.04 with network printing not working, all the problems with Pulse audio, and the weird graphical glitches I've seen.

You can't please everyone. So I guess that is why there is so many Linux distributions to choose from.

In this tug-o-war between stability, and leading edge features, I have to choose stability every time. New features will come in time. But if I cannot use the operating system and it's applications as I need, because things do not work, or are not stable. Then it is useless to me.

Let's hope someone takes notice soon.

Take care.

Thanx for your understanding. I'll wait for the time being and 'll keep on using ubuntu 7.10 for another half a year 1f40 or so. Perhaps ubuntu 8.10 will be better. 7.10 is supported for another year.

I reported a bug at https://bugs.launchpad.net/ubuntu/+bug/237759

I certainly hope that someone of the ubuntu team will take notice soon.

Jeroen

Thanks, but no, my username was already in that group. My printer is NOT a USb printer. Its a parallel HP Laserjet 4000 printer connected to a sitecom printserver. The printserver is connected to my router with a fixed IP address. If I ping this IP nr, I receive nice answers. So the printserver is connected
In Gutsy I use printerpoort

and it works. In Hardy it doesn't.

doesn't see my printer and I can't print.

Does anyone have another idea?

Thanks

As far as I know the lpd command is lpd://192.168.2.10/L1 how about trying that?
Also try the ipp command using: ipp//192.168.2.10/ipp/P1
or ipp//192.168.2.10:631/ipp/P1

I have an epson that used to work under gutsy but doesn't under hardy, printing via a 3com print server. Unfortunately the printserver itself died a day ago, so perhaps that was the main problem for me!

However when it was working I setup a new printer under the GNOME printing screen from the main menus and chose "LPD" as the type of printer. The key entry was the "L1" which isn't intuitive but has to be used and must go in the queue field for the thing to work. It did the trick for me, hope it works for you, otherwise I can't help you more.

I also lost printing ability after Hardy installed. I send a job to cups, then cups stops it. I checked dmesg and this is what I get:

[16394.427672] audit(1211154077.674:6): type=1503 operation="inode_permission" requested_mask="::rw" denied_mask="::rw" name="/dev/tty" pid=23459 profile="/usr/sbin/cupsd" namespace="default"

It is a usb printer and appears to be connected:

[15619.787827] usblp0: USB Bidirectional printer dev 4 if 0 alt 0 proto 2 vid 0x04B8 pid 0x0005
[15619.787851] usbcore: registered new interface driver usblp

I thought i 1f40 t may be a permission issue, so I tried to print as root. Same thing.

I looked in /var/log/cups/error_log and got this:

E [18/May/2008:16:27:12 -0700] [Job 114] ijsgutenprint: the version of Gutenprint software installed (5.0.2) does not match the PPD file (5.0.1).
E [18/May/2008:16:27:12 -0700] [Job 114] ijsgutenprint: bad key code -4

So I tried reinstalling the printer. Nope.

Any ideas?

Adding yourself to the USB users might help if you've got an USB connected printer. There are threads about that issue.

This thread is about printing via the router to a printserver connected printer.

The lpd command responds that it is connected to the printer. A print command from yesterday rolls out of the printer, but nothing happens but waiting for half an hour.

Three days later still waiting....

Doesn't anybody have this problem. Doesn't somebody have a solution? I0d like to be able to print. from hardy.

Adonet,

I just found your thread and like you, am having trouble printing via LPD in Hardy. I've installed Hardy on my Acer 3003LCi laptop. My printer is a Samsung ML1710 served by a Trendnet ethernet to USB print server.

With Dapper through Gutsy, it has been pretty easy to get printing configured on this machine. But with Hardy, I still haven't had any luck. When I try to print a document, the Samsung starts to run, but then enters an error state. So I have to power off the printer to reset it. All other printers on the network print without issue.

So you are not alone, but I have not yet solved the problem. If I find something, I will let you know.

Red

Putting it in complain mode worked for me... what now?

Hello again,

I was finally able to try putting AppArmor into complain mode and that allowed my Hardy install to print to my Samsung printer. So what do I need to do from here to re-enable AppArmor but still continue getting printing to work? Is there a thread that describes the process to reconfigure around offending issues? This seems to be my last problem with Hardy that I need to get resolved.

Thanks for everyone help so far.

Red

I'm glad you can print at last. Look for an AppArmor specialist who might help you.

AppArmor in complainmode didn't do anything for me. So that isn't the problem for me.
Is there anybody who didn't make a fresh install of Hardy, but an upgrade from gutsy who has the same problem?

Is booting Hardy with the older Gutsy kernel probably a solution?